Chore(deps): Bump dorny/paths-filter from 3.0.2 to 4.0.1#552
Conversation
Bumps [dorny/paths-filter](https://github.com/dorny/paths-filter) from 3.0.2 to 4.0.1. - [Release notes](https://github.com/dorny/paths-filter/releases) - [Changelog](https://github.com/dorny/paths-filter/blob/master/CHANGELOG.md) - [Commits](dorny/paths-filter@de90cc6...fbd0ab8) --- updated-dependencies: - dependency-name: dorny/paths-filter dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
PR #552 Evaluation: Bump Summary: ✅ Safe to mergeThis is a straightforward, low-risk dependency bump. The PR changes a single line in one file — the pinned SHA for What the diff doesThe only change is in Release notes between v3.0.2 → v4.0.1Three releases span this bump:
API / Syntax compatibility checkI compared the
And the outputs:
No inputs were added, removed, renamed, or had their defaults changed between v3 and v4. The full set of inputs ( What actually changed under the hood
Risk assessment
RecommendationApprove and merge. No workflow syntax changes are needed. The bump is purely a runtime upgrade (Node 20 → 24) plus a bugfix and an additive feature. Your specific usage of |
Bumps dorny/paths-filter from 3.0.2 to 4.0.1.
Release notes
Sourced from dorny/paths-filter's releases.
Changelog
Sourced from dorny/paths-filter's changelog.
... (truncated)
Commits
fbd0ab8feat: add merge_group event supportefb1da7feat: add dist/ freshness check to PR workflowd8f7b06Merge pull request #302 from dorny/issue-299addbc14Update README for v49d7afb8Update CHANGELOG for v4.0.0782470cMerge branch 'releases/v3'd1c1ffeUpdate CHANGELOG for v3.0.3ce10459Merge pull request #294 from saschabratton/master5f40380feat: update action runtime to node24668c092Merge pull request #279 from wardpeet/patch-1Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)